⚠️ No Changeset found

Latest commit: fd2732e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

View your CI Pipeline Execution ↗ for commit fd2732e

☁️ Nx Cloud last updated this comment at 2026-01-23 08:41:55 UTC

npm i https://pkg.pr.new/@tanstack/angular-form@1963

npm i https://pkg.pr.new/@tanstack/form-core@1963

npm i https://pkg.pr.new/@tanstack/form-devtools@1963

npm i https://pkg.pr.new/@tanstack/lit-form@1963

npm i https://pkg.pr.new/@tanstack/react-form@1963

npm i https://pkg.pr.new/@tanstack/react-form-devtools@1963

npm i https://pkg.pr.new/@tanstack/react-form-nextjs@1963

npm i https://pkg.pr.new/@tanstack/react-form-remix@1963

npm i https://pkg.pr.new/@tanstack/react-form-start@1963

npm i https://pkg.pr.new/@tanstack/solid-form@1963

npm i https://pkg.pr.new/@tanstack/solid-form-devtools@1963

npm i https://pkg.pr.new/@tanstack/svelte-form@1963

npm i https://pkg.pr.new/@tanstack/vue-form@1963

commit: fd2732e

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.33%. Comparing base (6892ed0) to head (fd2732e).
⚠️ Report is 124 commits behind head on main.

@@            Coverage Diff             @@
##             main    #1963      +/-   ##
==========================================
+ Coverage   90.35%   93.33%   +2.97%     
==========================================
  Files          38        2      -36     
  Lines        1752       60    -1692     
  Branches      444        4     -440     
==========================================
- Hits         1583       56    -1527     
+ Misses        149        4     -145     
+ Partials       20        0      -20     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

CI is green and coverage is fixed.
This PR is ready for review.

Wait, I'm confused - shouldn't this be avoided as-of https://github.com/TanStack/form/releases/tag/%40tanstack%2Fvue-form%401.27.7 ?

I checked the 1.27.7 changes and this does not reintroduce the behavior avoided there.

The change in 1.27.7 avoids subscribing to the full field state to prevent unnecessary updates.
This PR follows the same intent by narrowing subscriptions further in array mode, limiting value tracking to length-only while still respecting the current store architecture.

If there’s a specific concern with multiple useStore subscriptions in Vue, I’m happy to adjust the approach.

I see this mentions Vue but the behavior also happens in react

@crutchcorn Yeah, it should be avoided, but while it is fixed in React, in Vue, it still re-renders each field after each change in any array field that significantly affects the performance. You could see the repro from the linked issue